Add assignability rules for when the target is a conditional type #27932
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
weswigham
force-pushed
the
infer-conditional-class-this
branch
from
7652906 to
f590103
Compare
|
When you write:
By instantiated are you referring to the instantiation of the infer parameters? Would it be possible to write a small example that shows the difference between the proposed behaviour, and the behaviour if you only consider the uninstantiated true constraint (as opposed to the intersection)? I have a hard time translating the rules into concrete examples, so it would be greatly appreciated! |
This was referenced Dec 4, 2018
|
Does this address the unsoundness in #26945? |
sandersn
added
the
Experiment
|
This experiment is pretty old, so I'm going to close it to reduce the number of open PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Inspired by looking into #27014
Fixes #26933
Steals from #27589
This adds assignability rules for relating types when the target is a conditional type. We only check for conditional type target assignability when:
neverGiven these circumstances, a type is assignable to the conditional in question if
true(yet hasinfertypes, preventing simplification) and it is assignable to the intersection of the instantiated constraint of thetruebranch and the uninstantiated constraint (this allows for "independent" infer types to not interfere with true branch assignability, whilst still preserving the assignment-blocking part of the existential-like behavior of theinfertypes).